Repository navigation
ci: add an optional npm dependency report - #240
Open
PresentJay wants to merge 1 commit into
Open
PresentJay wants to merge 1 commit into
PresentJay wants to merge 1 commit into
Conversation
Author
|
I contribute to zero-shelter and am exploring whether an occasional HTML dependency report is useful for html-minifier-terser. The saved npm capture had no findings. Would a manually requested artifact be worth having alongside your existing checks? I can withdraw it if your current tooling already gives you the dependency view you need. |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I tried a manual HTML view of html-minifier-terser's committed npm tree while exploring where this report is useful. I contribute to zero-shelter, and used AI assistance for this PR and validation. The saved audit reported no dependency findings; this proposal is for optional reporting.
Only
.github/workflows/dependency-report.ymlis added. Dependency triage report starts throughworkflow_dispatchand requestscontents: read. It runsnpm audit --package-lock-only --ignore-scripts, passes that one npm report to pinnedzero-shelter@0.0.10, and retains generated HTML for 7 days. It installs no project dependencies, runs no project lifecycle scripts and accepts no baseline. Existing build, test and publishing workflows remain in place. Finding exit1and judgement-error exit2remain failures. Node 24 is used only for this report job.Stored validation at
f863b9431e23had 0 raw records, 0 merged findings and 0 outstanding findings; audit, JSON and HTML commands exited0. YAML, shell syntax and diff checks passed, and manifest and lockfile were unchanged. These are saved results, not a fresh scan. Application tests and a hosted manual run were not verified in that validation.The report cannot establish runtime reachability or overall security. Audit sends dependency metadata to the configured registry;
npxdownloads and executes third-party CLI code in CI, even with a read-only repository token.Would an occasional manual report fit your dependency review workflow? I can withdraw it if your current tooling already provides enough.